Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aggregate packages #3689

Merged
merged 9 commits into from
Feb 11, 2021
Merged

Aggregate packages #3689

merged 9 commits into from
Feb 11, 2021

Conversation

Rosuavio
Copy link
Contributor

@Rosuavio Rosuavio commented Jan 25, 2021

Step towards #3594

Adds a project that builds a package that aggregates together other UI control packages.

PR Type

What kind of change does this PR introduce?

  • Feature
  • Refactoring (no functional changes, no api changes)
  • Build or CI related changes

What is the current behavior?

What is the new behavior?

PR Checklist

Please check if your PR fulfills the following requirements:

  • Tested code with current supported SDKs
  • Pull Request has been submitted to the documentation repository instructions. Link:
  • Sample in sample app has been added / updated (for bug fixes / features)
  • New major technical changes in the toolkit have or will be added to the Wiki e.g. build changes, source generators, testing infrastructure, sample creation changes, etc...
  • Tests for the changes have been added (for bug fixes / features) (if applicable)
  • Header has been added to all new source files (run build/UpdateHeaders.bat)
  • Contains NO breaking changes

Other information

@ghost
Copy link

ghost commented Jan 25, 2021

Thanks RosarioPulella for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌

@ghost ghost requested review from michael-hawker, azchohfi and Kyaa-dost January 25, 2021 18:39
@Rosuavio Rosuavio mentioned this pull request Feb 1, 2021
8 tasks
Comment on lines 28 to 41
<PackagingOutputs Remove="@(PackagingOutputs)" Condition="'%(PackagingOutputs.Filename)%(PackagingOutputs.Extension)' == 'Microsoft.Toolkit.Uwp.UI.Controls.Core.pri'" />
<PackagingOutputs Remove="@(PackagingOutputs)" Condition="'%(PackagingOutputs.Filename)%(PackagingOutputs.Extension)' == 'Microsoft.Toolkit.Uwp.UI.Controls.Primitives.pri'" />
<PackagingOutputs Remove="@(PackagingOutputs)" Condition="'%(PackagingOutputs.Filename)%(PackagingOutputs.Extension)' == 'Microsoft.Toolkit.Uwp.UI.Controls.Media.pri'" />
<PackagingOutputs Remove="@(PackagingOutputs)" Condition="'%(PackagingOutputs.Filename)%(PackagingOutputs.Extension)' == 'Microsoft.Toolkit.Uwp.UI.Controls.DataGrid.pri'" />
<PackagingOutputs Remove="@(PackagingOutputs)" Condition="'%(PackagingOutputs.Filename)%(PackagingOutputs.Extension)' == 'Microsoft.Toolkit.Uwp.UI.Controls.Markdown.pri'" />
<PackagingOutputs Remove="@(PackagingOutputs)" Condition="'%(PackagingOutputs.Filename)%(PackagingOutputs.Extension)' == 'Microsoft.Toolkit.Uwp.UI.Controls.Layout.pri'" />
<PackagingOutputs Remove="@(PackagingOutputs)" Condition="$([System.String]::new('%(PackagingOutputs.TargetPath)').StartsWith('Microsoft.Toolkit.Uwp.UI.Controls.Primitives\'))" />
<PackagingOutputs Remove="@(PackagingOutputs)" Condition="$([System.String]::new('%(PackagingOutputs.TargetPath)').StartsWith('Microsoft.Toolkit.Uwp.UI.Controls.Core\'))" />
<PackagingOutputs Remove="@(PackagingOutputs)" Condition="$([System.String]::new('%(PackagingOutputs.TargetPath)').StartsWith('Microsoft.Toolkit.Uwp.UI.Controls.Media\'))" />
<PackagingOutputs Remove="@(PackagingOutputs)" Condition="$([System.String]::new('%(PackagingOutputs.TargetPath)').StartsWith('Microsoft.Toolkit.Uwp.UI.Controls.DataGrid\'))" />
<PackagingOutputs Remove="@(PackagingOutputs)" Condition="$([System.String]::new('%(PackagingOutputs.TargetPath)').StartsWith('Microsoft.Toolkit.Uwp.UI.Controls.Markdown\'))" />
<PackagingOutputs Remove="@(PackagingOutputs)" Condition="$([System.String]::new('%(PackagingOutputs.TargetPath)').StartsWith('Microsoft.Toolkit.Uwp.UI.Controls.Layout\'))" />
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@michael-hawker I don't have a lot of knowledge on how the original "RemoveUnwantedPri" code in other projects but, this code seemed to have fixed issues when including the package in a test project for me, let me know if this code here makes sense.

Also there has to be a better way to write this, I am not that familiar with what syntax is available here. I anyone wants to help me clean this up.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if this is because we're using ProjectReference,.. @azchohfi could we just use PackageReference here and see if that removes the problem? Or that's going to be an issue, eh? As then we'd have to build it after the others?

But otherwise, yes I think we need these to work-around how the build system works. Ideally these packages don't contain any content, so we may need to look at the final nuget package built in the end.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would make our life a mess to sync the version. I don't see why we would need these, as the package itself should not contain anything. If adding the <IncludeBuildOutput>false</IncludeBuildOutput> don't fix it, which I think it will, we could always just use a nuspec.

@Rosuavio
Copy link
Contributor Author

Rosuavio commented Feb 2, 2021

I tested this by taking the published "Controls" package into UWP app and using the InfiniteCanvas, testing if other controls can be used just fine would be good.

@Rosuavio Rosuavio changed the title Aggregate packages [WIP] Aggregate packages Feb 4, 2021
@Rosuavio Rosuavio marked this pull request as draft February 4, 2021 17:22
@Rosuavio Rosuavio changed the title [WIP] Aggregate packages Aggregate packages Feb 8, 2021
@Rosuavio Rosuavio marked this pull request as ready for review February 8, 2021 20:19
@michael-hawker michael-hawker added the next preview ✈️ Label for marking what we want to include in the next preview release for developers to try. label Feb 8, 2021
@michael-hawker
Copy link
Member

@azchohfi we wouldn't expect there to be a dll here, eh?

image

@azchohfi
Copy link
Contributor

azchohfi commented Feb 9, 2021

There will still be an auto generated class for assembly version, etc, so it will, by default, generate a DLL. There is a property to exclude it. Let me find it.

@azchohfi
Copy link
Contributor

azchohfi commented Feb 9, 2021

<IncludeBuildOutput>false</IncludeBuildOutput>

Only include depedencies in package.
@Rosuavio
Copy link
Contributor Author

Rosuavio commented Feb 9, 2021

Thanks @azchohfi, from the smoke tests it looks like it worked.

@michael-hawker
Copy link
Member

Looks like we're clean now!

image

@RosarioPulella wondering if we can remove the PRI work-arounds now that it's not building the DLL? Want to give that a quick test on your local branch and see?

@azchohfi otherwise I think we're all good, eh?

@Rosuavio
Copy link
Contributor Author

@RosarioPulella wondering if we can remove the PRI work-arounds now that it's not building the DLL? Want to give that a quick test on your local branch and see?

Worked just fine locally. Feel free to test it from the nuget feed once CI finishes.

@ghost
Copy link

ghost commented Feb 11, 2021

Hello @michael-hawker!

Because this pull request has the auto merge :zap: label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@michael-hawker
Copy link
Member

Looks great, new build works the same. 🎉

@michael-hawker michael-hawker merged commit c7bdaf2 into CommunityToolkit:dev/split-controls Feb 11, 2021
@Rosuavio Rosuavio deleted the aggregate-packages branch February 12, 2021 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto merge ⚡ build 🔥 controls 🎛️ for-review 📖 To evaluate and validate the Issues or PR functional testing required 📌 next preview ✈️ Label for marking what we want to include in the next preview release for developers to try.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants